fedora-docs-l10n/package-maintainers/master/pages/Package_Retirement_Process

Zen

	English	French	Actions
	Package Retirement Process
	When a package reaches the end of its useful life, the Package Retirement Process lets other people — and automated processes! — know both not to expect any more releases, and why it was removed. The process is governed by xref:fesco::Policy_for_orphan_and_retired_packages.adoc[Policy for Orphan and Retired Packages].
	A common situation that involves, among other tasks, retiring a package is renaming a package, or replacing it with another that provides compatible functionality. For handing such situation, see xref:packaging-guidelines::index.adoc#renaming-or-replacing-existing-packages[the relevant packaging guidelines].
	What can be retired
	Packages can normally only be retired in the following branches:
	xref:releases::rawhide.adoc[Rawhide]
	xref:releases::branched.adoc[Branched] (until the Final Freeze)
	EPEL branches (`epel7`, `epel8`, `epel9`, and the corresponding `-next` branches) - see xref:epel::epel-policy-retirement.adoc/[EPEL Retirement Policy] for additional requirements
	Procedure
	Please execute the following steps in the order indicated.
	RPM
	If the package is being replaced by some other package, ensure that the `Obsoletes`/`Provides` tags are properly set by the new package as specified in xref:packaging-guidelines::index.adoc#renaming-or-replacing-existing-packages[Renaming/Replacing Guidelines].
	Git
	Run `fedpkg retire DESCRIPTION` in Rawhide. `DESCRIPTION` should explain why the package was retired. Examples of good messages are _Obsoleted by <new package>_ and _Renamed to <new package>_.
	`fedpkg retire` removes all files from the branch, adds file `dead.package` that contains `DESCRIPTION`, and pushes the changes.
	If Branched currently exists and Final Freeze has not started yet, prevent the package from being released by merging (or cherry-picking, etc.) the retirement commit into that branch. It is not necessary to run `fedpkg retire` separately for Branched.
	Do not run `fedpkg retire` or merge a retirement commit for any supported or end-of-life Fedora release branch. Packages must not be retired from stable releases.
	If the package is included in EPEL, consider also xref:epel::epel-policy-retirement.adoc[EPEL Retirement policy].
	fedora-obsolete-packages
	Consider what will happen to systems which have the now-retired packages installed. Generally, such packages will simply remain on the system as it is updated, becoming increasingly outdated. If this is not acceptable, such as if there are upgrade path issues or security concerns, add your package to https://src.fedoraproject.org/rpms/fedora-obsolete-packages/[fedora-obsolete-packages].
	Comps
	Remove the package from https://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups[comps] if it is listed.
	Spins
	Remove the package from any https://pagure.io/fedora-kickstarts[spin kickstart file].

Loading…

mt:weblate-translation-memory

Suggestion added

English

French 9 characters edited

4 months ago

None

String updated in the repository

English

French 0 characters edited Current translation Empty

4 months ago

Browse all string changes

Things to check

Suggestions

There is 1 suggestion for this string.

View

Glossary

English	French
No related strings found in the glossary.

String information

Source string description

type: Title ==

Flags

no-wrap, placeholders:r"`[\w\d -_<>(){}\[\]@$;.\*+=]*`":r"(link:)?https?://[\w\d\-_#?&%=\./]*":r"xref:[\w\d\-_/]*\.adoc(#[\w\d\-_/]*)?"

Source string location

pages/Package_Retirement_Process.adoc:29

String age

4 months ago

Last updated

4 months ago

Source string age

4 months ago

Translation file

po/fr/master/pages/Package_Retirement_Process.po, string 9